- 6 minutes to read

Release Notes

Prerequisites for the Nodinite Mule ESB Logging agent

Unlock seamless integration and powerful monitoring by preparing your environment for the Nodinite Mule ESB Logging Agent. This guide covers everything you need for a successful installation and operation.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-monitor-waveform Mule ESB Logging Agent) end subgraph "Anypoint instances in the cloud" roCloudhubAPI(fal:fa-cloud Cloudhub API)-->roIS(fal:fa-database Internal storage) roNI --> | API | roCloudhubAPI roFlow2(fal:fa-sitemap Flow) --> | Log4J | roIS end subgraph "Mule ESB instance on-premise" roFolder(fal:fa-folder Folder) roNI --> | SMB | roFolder roFlow(fal:fa-sitemap Flow) --> | Log4J | roFolder end
*Architecture overview: The Nodinite Mule ESB Logging Agent supports both on-premise and cloud-based MuleSoft environments.*

We recommend installing this agent close to your Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server).

Verified Topic
Software Requirements
What folder rights does the Mule ESB Logging Agent require?
What Anypoint Cloudhub rights does the Mule ESB Logging Agent require?
What Windows User Rights does the Mule ESB Logging Agent require?
What Firewall settings are required for the Mule ESB Logging Agent?

Software Requirements

The Mule ESB Logging Agent is a Windows Service and is usually installed on the Nodinite application server.

Product
Windows Server Windows 2025
Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.5 or later

Supported Versions

Cloud technologies evolve rapidly, and MuleSoft deprecates older API versions regularly. Nodinite always supports the APIs supported by MuleSoft. Update Nodinite and the Mule ESB Logging Agent as needed to stay current.

Subscribe to our Release Notes to stay informed about updates.

What folder rights does the Mule ESB Logging Agent require?

If you use Mule ESB on-premise with the Log4J file appender, logged events are created on local disk or a Windows File share (SMB).
The Mule ESB Logging Agent must have Read, Write, and Change permissions to consume these events.

What Anypoint Cloudhub rights does the Mule ESB Logging Agent require?

  • The agent uses the MuleSoft Anypoint Cloudhub API to read logged events with tracked properties. Grant the agent the necessary access rights as described in the Configuration.

What Windows User Rights does the Mule ESB Logging Agent require?

The agent is installed as a Windows Service, usually on the Nodinite application server. Virtual machines are supported.

What Firewall settings are required for the Mule ESB Logging Agent?

Where you install the Nodinite Mule ESB Logging Agent in relation to the Nodinite Log API, your on-premise Mule ESB log folders, and the Anypoint Platform determines your firewall configuration. The agent is a Windows Service that only opens outbound connections; the Nodinite Monitoring Service never calls it. The diagram shows every host involved, with the agent on its own server; each arrow starts at the side that opens the connection.

graph LR subgraph "Nodinite Core Services Server" roLogAPI(fa:fa-cloud-arrow-down Log API) end subgraph "Nodinite Agent Server" roNI(fa:fa-monitor-waveform Mule ESB Logging Agent) end subgraph "Target: Mule ESB Server (on-premise)" roFolder(fa:fa-folder Log folder or SMB file share) end subgraph "Target: Anypoint Platform (CloudHub)" roCloudhubAPI(fa:fa-cloud CloudHub API) end subgraph "Domain Controller" roDC(fa:fa-building-shield Active Directory) end subgraph "DNS Server" roDNS(fa:fa-signs-post DNS) end roNI --> |"445, 135-139"| roFolder roNI --> |"443"| roCloudhubAPI roNI --> |"Log API site port"| roLogAPI roNI --> |"88, 389, 636"| roDC roNI --> |"53"| roDNS

Network diagram: the agent reads Log4J files from on-premise Mule servers over SMB and logged events from the CloudHub API, then posts Log Events to the Log API.

Note

When the agent runs on the Core Services Server (the typical installation), you need no firewall rule between the agent and the Log API.

Between the Mule ESB Logging Agent and the Mule ESB servers

Required for on-premise Mule ESB. The agent reads the Log4J log files from a local folder or an SMB file share on each Mule server.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Target (Mule ESB Server) TCP 445 Direct-hosted SMB traffic SMB 2.0 and 3.0 (recommended)
Outbound Agent Server Target (Mule ESB Server) TCP/UDP 135-139 Microsoft file sharing (NetBIOS) Legacy SMB 1.0/CIFS only; consider disabling SMB 1.0
Inbound Target (Mule ESB Server) Agent Server TCP/UDP 135-139, 445 Response traffic Automatically allowed by stateful firewall inspection

Tip

Grant the agent's service account Read permissions on the Mule ESB log folders. See File and printer sharing ports and Internet firewalls can prevent browsing and file sharing.

Between the Mule ESB Logging Agent and the Domain Controller

Required when the agent reads SMB file shares with a domain account.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Domain Controller TCP/UDP 88 Kerberos authentication Required for domain authentication
Outbound Agent Server Domain Controller TCP/UDP 389 LDAP Standard LDAP queries
Outbound Agent Server Domain Controller TCP 636 LDAPS (Secure LDAP) Required for LDAPS authentication or querying certificates from AD

Between the Mule ESB Logging Agent and the CloudHub API

Required for CloudHub. The agent reads logged events with tracked properties from the CloudHub API. All traffic is outbound HTTPS; MuleSoft needs no inbound rule. Allow the hostname of your control plane, as listed in Anypoint Platform hostnames and allowlists.

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Target (Anypoint Platform, anypoint.mulesoft.com) TCP (HTTPS) 443 CloudHub API calls US control plane (default)
Outbound Agent Server Target (Anypoint Platform, eu1.anypoint.mulesoft.com) TCP (HTTPS) 443 CloudHub API calls EU control plane
Outbound Agent Server Target (Anypoint Platform, gov.anypoint.mulesoft.com) TCP (HTTPS) 443 CloudHub API calls US Government control plane
Inbound Target (Anypoint Platform) Agent Server TCP 443 Response traffic Automatically allowed by stateful firewall inspection

Tip

The account needs rights to read logged events and tracked properties; see Configuration. For hybrid landscapes (on-premise and CloudHub), open both the SMB and the CloudHub hops.

Between the Mule ESB Logging Agent and the Log API

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server Core Services Server TCP (HTTPS/HTTP) Log API site port Post Log Events to the Log API v7. The Log API is its own IIS web site; port set per environment in the Portal (Servers step). Use HTTPS when the agent and the Log API are on different servers. Match the LogAPI address in the Configuration

Between the servers and DNS

Direction Source Destination Protocol Port(s) Purpose Notes
Outbound Agent Server DNS Server TCP/UDP 53 Name resolution Resolve the Mule servers, the Anypoint hostnames, the Domain Controller, and the Core Services Server. A local hosts file can replace DNS

Important

Stateful Firewalls: Most Windows Firewall implementations are stateful, so response traffic for established outbound connections is allowed automatically. The inbound response rules above are for reference and troubleshooting.

Frequently asked questions

Find solutions to common problems and FAQs for the Nodinite Mule ESB Logging Agent in the Troubleshooting user guide.

About Mule ESB

  • Anypoint Studio 6 requires Java8

Next Steps

Add or manage a Monitoring Agent Configuration
Install the Mule ESB Logging Agent

Administration
Monitoring Agents